I have confirmed this as fixed in the most recent internal beta, so it'll be solved for the next public release.